Autonomous secrets management for a temporary shared access signature service

ABSTRACT

Various methods and systems are provided for autonomous secrets management for a temporary shared access signature (“SAS”) service. Input for a temporary access request for an account resource, is received from a client. The temporary access request is validated, based on communicating a validation request to the secrets management service (“SMS”) that can be utilized to store, renew and distribute secrets in a distributed computing environment. Validating the temporary access request is based on determining a storage account location path for SAS keys that provide temporary access to account resources. An access policy associated with the temporary access request is accessed. An SAS key request, associated with temporary access request, is communicated to the SMS. The SAS key request includes at least a portion of the access policy. An SAS key is received from the SMS. The SAS key, for access to the account resource, is communicated to the client.

BACKGROUND

Generally, secrets such as certificates, passwords, storage account keys, shared access signatures (SAS), and the like have a life cycle. At the end of life, the secret can expire or otherwise become invalid and/or untrusted. As such, secrets need to be renewed from time to time. In systems, such as data centers in which resources such as secrets can be distributed, managing such distributed secrets poses various challenges.

SUMMARY

Techniques herein relate to autonomous secrets renewal and distribution and may be implemented in a distributed computing environment. A secrets management service can be utilized to store, renew and distribute secrets such as certificates, storage account keys, shared access signatures, connection strings, custom types, and the like. In the context of distributed computing, a datacenter secrets management service (“dSMS”) can orchestrate secrets renewal and distribution within the distributed computing environment. When a customer sets up a desired service, the customer can onboard secrets for the service to the dSMS. In some embodiments, a corresponding service model and/or configuration file for the service references the secrets by their path in dSMS. The secrets are initially deployed, for example on a node or virtual machine running the service, after which, dSMS can automatically renew the secrets according to the specified rollover policy, and polling agents for an associated service can fetch updates from dSMS. In this manner, secrets can be automatically renewed without manual orchestration and/or the need to redeploy services.

In one example scenario, a secrets management service such as dSMS can be utilized to autonomously rollover client certificates. After onboarding the secrets into dSMS, a client app and a corresponding service app can fetch renewed certificates from dSMS. In some embodiments, dSMS distributes multiple versions of a client certificate to facilitate an attempted authentication using a prior version of the certificate. Additionally and/or alternatively, when dSMS renews a certificate, dSMS can implement a secrets release delay, waiting for a configurable time period to deliver the renewed certificate to the client app, while advertising the renewed certificate to the server. As such, a secrets release delay can provide a service app with time to pick up the renewed certificate before releasing it to the client app.

In another example scenario, a secrets management service such as dSMS can be utilized to autonomously rollover storage account keys. Generally, primary and secondary keys for a storage account are rolled over on a predefined schedule in an interleaving fashion. In an example in which keys have a two year expiration, every year, either the primary or the secondary key is renewed and distributed. dSMS can generate a dependent shared access signature using a designated active key which has farther expiration. In some embodiments, when an expiring storage account key is rolled over, dSMS can regenerate any dependent shared access signatures using the other key prior to rolling over the expiring key.

In some embodiments, a secrets management service such as dSMS can track delivery of updated secrets to secrets recipients. For example, dSMS can maintain a repository which tracks the state of agents operating on each secrets recipient in a computing fabric, updating the state based on information in a periodic polling request. Additionally and/or alternatively, dSMS can maintain a repository which tracks the state of a particular rollover. When delivery of a renewed secret to all the agents configured to receive it has been confirmed, the rollover can be designated complete.

In some embodiments, a secrets management service such as dSMS can be utilized to autonomously rollover secrets for services sharing secrets with other services across regional or other scope boundaries. For example, a cross-scope secrets management service can be utilized to orchestrate renewal and distribution of secrets across scope boundaries. In some embodiments, locally scoped secrets management services subscribe to receive updates from the cross-scope secrets management service. As secrets are renewed, they are automatically propagated to the subscribing local scope and distributed by the local secrets management service.

In some embodiments, a secrets management service such as dSMS can deliver secrets to a service application using a secure Binary Large Object (“blob”), which is an encrypted structured binary sequence of data. For example, dSMS can generate a secrets package including a secure blob which contains secrets managed by dSMS for a particular service. In some embodiments, dSMS includes some certificates in the secrets package outside of the secure blob. Advantageously, the secure blob is encrypted during transport and stored encrypted. In some embodiments, the secure blob and/or a corresponding service object can be version controlled. As such, when a polling request indicates a particular agent needs an update based on a current version used by the agent, dSMS can reply with the latest secrets package and/or secure blob.

In some embodiments, autonomous secrets rollover includes secret staging, which can be implemented on a client, a service, or both. In a client-side staging model, a secrets management service such as dSMS pushes renewed secrets to a container, and the secrets are securely cached in a staged mode. A corresponding application and/or an external orchestration engine can determine when to begin using the secret, and can trigger the unstaging of the secret for active use. In a service side-staging model, a secrets management service such as dSMS rotates secrets one update domain at a time.

In some embodiments, a secrets management service, such as dSMS, provides support for autonomous secrets management for a managed service identity. Secrets management can include using the identity name (e.g., identity identifier), of a managed service, by way of an abstracted implementation, to retrieve a security token from a secret token service (e.g., datacenter secret token service—identity provider) dSTS. Secrets management also includes autonomous secrets renewal and distribution of secrets for the managed service operating with the dSTS.

In some embodiments, a secrets management service, such as dSMS, provides support for autonomous secrets management for a temporary shared access signature (SAS) service. The temporary SAS service operates with access polices to provide temporary access to storage accounts, based on storage account keys. Rolling over of storage account keys and/or SASes associated with the temporary SAS service is delegated and autonomously performed using dSMS.

As such, autonomous secrets rollover can be achieved using the autonomous orchestration techniques for secrets renewal and distribution described herein. A secrets management service, such as dSMS, can achieve autonomous secrets rollover in a distributed computing environment. In various embodiments, dSMS can autonomously rollover client certificates for authentication of users who access a security critical service, autonomously rollover storage account keys, track the delivery of updated secrets to secrets recipients, autonomously rollover secrets for services sharing secrets with other services across regional or other scope boundaries, deliver secrets to a service application using a secure blob, and/or facilitate autonomous rollover using secrets staging.

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used in isolation as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in detail below with reference to the attached drawing figures, wherein:

FIG. 1 is a block diagram of an autonomous secrets management system, in accordance with embodiments described herein;

FIG. 2 is a block diagram of an autonomous secrets management system, in accordance with embodiments described herein;

FIG. 3 is a block diagram of an autonomous client certificate management system, in accordance with embodiments described herein;

FIG. 4 is a block diagram of an autonomous cross-scope secrets management system, in accordance with embodiments described herein;

FIG. 5 is a block diagram of an autonomous secrets management system with staging, in accordance with embodiments described herein;

FIG. 6 is a flow diagram showing an example method for managing secrets, in accordance with embodiments described herein;

FIG. 7 is a flow diagram showing an example method for agent state tracking, in accordance with embodiments described herein;

FIG. 8 is a flow diagram showing an example method for rollover tracking, in accordance with embodiments described herein;

FIG. 9 is a flow diagram showing an example method for managing secrets, in accordance with embodiments described herein;

FIG. 10 is a flow diagram showing an example method for autonomous rollover of client certificates, in accordance with embodiments described herein;

FIG. 11 is a flow diagram showing an example method for managing secrets across scope boundaries, in accordance with embodiments described herein;

FIG. 12 is a flow diagram showing an example method for managing secrets across regional boundaries, in accordance with embodiments described herein;

FIG. 13A-13B is a flow diagram showing an example method for managing secrets across scope boundaries, in accordance with embodiments described herein;

FIG. 14A-14B is a flow diagram showing an example method for managing secrets, in accordance with embodiments described herein;

FIG. 15A-15B is a flow diagram showing an example method for managing secrets, in accordance with embodiments described herein;

FIG. 16 is a block diagram of an example distributed computing environment suitable for use in implementing embodiments described herein; and

FIG. 17 is a block diagram of an example computing environment suitable for use in implementing embodiments described herein.

DETAILED DESCRIPTION

Overview

In conventional datacenters, techniques for managing secrets have several shortcomings. Current systems today pin a specific value of the secret based on credential type. For example, conventional systems generally pin the thumbprint of a certificate or a unique global name of a storage account key in the system. Further, rotating specific values through a distributed environment is challenging and computationally complex, and generally requires manual orchestration. For example, a customer administrator might manually renew secrets and ship them as deployed assets throughout a large distributed service running on physical nodes or virtual machines (“VM”). Before a service can make use of a renewed secret, the service needs to be manually configured to utilize the renewed secret, and the reconfigured service needs to be redeployed. This process may be repeated for multiple services across multiple regions which share secrets. These techniques require significant human intervention, which can be time consuming, inefficient, and susceptible to human error.

Relying on manual orchestration of secrets renewal can create various problems. For example, if a manual rollover has not been completed before a secret expires, a system outage can occur in which partners within the system cannot communicate because they have different versions of a secret. Such a system outage can occur even when a manual rollover occurs in a timely fashion, for example, because conventional techniques lack reporting systems to monitor the status of a rollover in progress. As such, despite beginning a rollover in a timely manner, the underlying secret may still expire before the rollover completely finishes. In some cases, the result may not be an outage, but may result in a security non-compliance. As such, processes to support autonomous secrets management are integral to the deployment of secrets in a distributed environment.

Embodiments described herein provide simple and efficient methods and systems for implementing autonomous secrets renewal and distribution. Generally, a secrets management service that stores secrets, such as certificates (e.g., chained, self-signed, imported, etc.), storage account keys, shared access signatures (“SAS”), connection strings, custom types, and the like, can be deployed. In the context of distributed computing, a datacenter secrets management service (“dSMS”) can be deployed to orchestrate secrets renewal and rollover within the distributed computing environment. A customer can define a secrets rollover policy for a particular distributed computing service to enable the service to create secrets in dSMS and reference the secrets in a corresponding service model by path in dSMS. The secrets required by the service are deployed to corresponding VMs and/or nodes by the distributed computing platform (e.g., computing fabric). dSMS can monitor the expiration of secrets and automatically renew secrets according to the defined rollover policy. Additionally and/or alternatively to auto-renewal, dSMS can renew a secret in response to a request for an on-demand rollover (e.g., during a breach scenario). VMs and/or nodes can run an agent that periodically polls dSMS to check if any of the secrets installed on the VMs and/or nodes have been renewed in dSMS. If a secret has been renewed, the renewed secret can be provided by dSMS and installed locally on the corresponding VMs and/or nodes. For some secrets, such as server SSL/TLS certificates, new versions can be linked to a previous version such that subsequent requests to the endpoint (container, app, node, etc.) automatically use the new certificates.

A secrets management service, such as dSMS, can be utilized in other scenarios besides a distributed computing environment. For example, dSMS can be utilized to autonomously rollover client certificates for authentication of users who access a security critical service (“service app”). A client app can be onboarded into dSMS so required can be deployed into the client app. The client app and/or service app can fetch renewed certificates using the polling technique described above. For example, a private key for a client certificate may be provided to the client app via a trusted endpoint of dSMS, while a public key may be provided to the service app in response to an anonymous call to a public endpoint of dSMS. In some embodiments, the service app is provided with the public certificate and its corresponding location in order to whitelist the certificate. When the client app connects to the service app, the client app provides the latest copy of the public certificate to the service app. If the public certificate is in the service app's whitelist, validation succeeds. Otherwise, the client app can retry with a prior version of the public certificate. Meanwhile, the service app can poll dSMS for an updated public certificate. Additionally and/or alternatively, the service app can include a worker thread which periodically polls dSMS for updates. In some embodiments, when dSMS renews the client certificate, dSMS can implement a secrets release delay, waiting for a configurable time period to deliver the renewed private key to the client app, while advertising the renewed public key to the server. As such, a secrets release delay can provide a service app with time to pick up the renewed public key before dSMS releases the renewed private key to the client app.

In some embodiments, a secrets management service such as dSMS can be utilized to autonomously rollover storage account keys. Generally, primary and secondary keys for a storage account are rolled over on a predefined schedule in an interleaving fashion. More specifically, the expiration of the primary key is separate from the expiration of the secondary key, and a customer can specify the renewal period in dSMS. In an example in which keys have a two year expiration, every year, either the primary or the secondary key is renewed and distributed. Any shared access signatures (“SASes”) which depend upon a storage account key can be generated and/or rolled over based on the expirations of the storage account keys. For example, dSMS can generate an SAS using the key which has farther expiration (i.e. the key which is valid for the longer period of time). Moreover, any SASes which depend on an expiring storage account key can be rolled over prior to rolling over the key upon which they depend. For example, if an expiring storage account key is being rolled over, dSMS can regenerate any dependent SASes using the other key prior to rolling over the expiring key. In this manner, rollover and expiration are predictable, and rollover can be performed without breaking a communication scheme.

In some embodiments, a secrets management service, such as dSMS, can track the delivery of updated secrets to secrets recipients. To accomplish this, dSMS can track the internal state of a secrets recipient (e.g., secret not delivered, secret delivered, secret confirmed), and update the state when the recipient polls dSMS. For example, dSMS can maintain a repository which tracks the state of agents operating on each secrets recipient in fabric. When an agent polls dSMS, it provides dSMS with secrets metadata (e.g., version, path, etc.). As such, dSMS can determine and update the internal state for the agent and/or distribute a renewed secret in the event the agent is using a prior version. Additionally and/or alternatively, dSMS can maintain a repository which tracks the state of a particular rollover (e.g., rollover started, rollover completed). When delivery of a renewed secret to all the agents configured to receive it has been confirmed, the rollover can be designated complete. In this manner, dSMS can track rollover progress and fire off desired alerts.

In some embodiments, a secrets management service, such as dSMS, can be utilized to autonomously rollover secrets for services sharing secrets with other services across regional or other scope boundaries. Generally, a cross-scope secrets management service can be utilized to renew and distribute secrets across scope boundaries. The cross-scope secrets management service can be deployed with a replication scope (e.g., global, specific region, etc.) with which secrets are shared. Locally scoped (e.g., regional) secrets management services can subscribe to receive updates from the cross-scope secrets management service. As secrets are renewed, they are automatically propagated to the subscribing local scope and distributed by the local secrets management service. In some embodiments, a rollover request received at a regional dSMS can trigger an on-demand fetch request to obtain the most recent secret from a cross-scope dSMS. State tracking can be performed across the composite cross-scope and local secrets management services to facilitate autonomous cross-scope rollovers without service interruption.

In some embodiments, a secrets management service, such as dSMS, can deliver secrets (e.g., to a node, service application, fabric controller, etc.) using a secure blob, which is an encrypted structured binary sequence of data. Generally, dSMS can support autonomous rollover of secrets in a distributed computing environment co-hosting various service applications. dSMS can generate a secrets package including a secure blob which contains secrets managed by dSMS for a particular service. The secrets package optionally includes certificates outside of the secure blob. The secrets package can be pushed to a container during the deployment of a corresponding service application. When a rollover occurs for a secret in a secure blob, dSMS generates a new secure blob containing the renewed secret. The next poll from an agent on the container will deliver the new secure blob to the container. As such, a secure blob can be used to deliver periodically refreshed secrets as they change.

In some embodiments, autonomous secrets rollover includes secret staging. Depending on the nature of a secret, applications which make use of the secret may require an orchestrated rollover across a service. Such orchestration can be achieved by a staging mechanism implemented on a client, a service, or both. In a client-side staging model, a secrets management service, such as dSMS, pushes renewed secrets to a container, and the secrets are securely cached in a staged mode. A corresponding application and/or an external orchestration engine can determine when to begin using the secret, and can trigger the unstaging of the secret for active use. In a service side-staging model, a secrets management service, such as dSMS, can rotate secrets according to a defined rollover policy, but defer pushing renewed secrets to all nodes of a tenant (or application) at once. Instead, dSMS pushes secrets to one update domain at a time and waits for feedback from application services deployed in the update domain prior to moving to the next update domain. In this manner, staging allows a phased rollover of new secrets by validating usage of new secrets prior to a full rollover across all services.

In some embodiments, a secrets management service, such as dSMS, provides support for autonomous secrets management for a managed service identity. In particular, secrets management can include using the identity name (e.g., identity identifier) of a managed service to retrieve a security token from a secret token service (e.g., datacenter secret token service—identity provider) dSTS. For example, a managed service on a node provides its identity name to a credentials manager on the node, the credentials manager having the most up-to-date secret. Based on providing its identity name to the credentials manager, and the credentials manager storing and accessing the secret for the managed service, a secret token is retrieved from dSTS. Secrets management also includes autonomous secrets renewal and distribution of secrets for the managed service operating with the dSTS. dSMS in collaboration with dSTS operate to manage the rollover process of secrets for managed service identities. dSMS ensures that the secret is rolled over before its expiration. dSMS further ensures that the secret is communicated to the node running the managed service.

In some embodiments, a secrets management service, such as dSMS, provides support for autonomous secrets management for a temporary shared access signature (SAS) service. In particular, the temporary SAS service operates based on portal-driven or RESTful temporary access policies and commands to provide access to a given storage account in the distributed computing environment. Specifically, the temporary SAS service operates with access polices to provide temporary access to storage accounts based on storage account keys. In operation, the temporary SAS service makes a validation call to the dSMS service to validate a temporary access request to an account resource using a temporary SAS. Upon validation of the temporary access request, the temporary SAS service then retrieves an access policy and requests a SAS key for a given expiration period for the temporary access to the account resource. Upon expiration of a temporary SAS, the SAS key does not get renewed and no service secrets are exposed. Secrets management for the temporary SAS service further includes rolling over of storage account keys and/or SASes associated with the temporary SAS service autonomously using dSMS. In this regard, while the temporary SAS service manages providing temporary access to an account resource, secrets management for the secrets (e.g., primary and second account keys) is autonomously managed using dSMS.

As such, autonomous secrets rollover can be achieved by autonomous orchestration of secrets renewal and distribution. A secrets management service, such as dSMS, can achieve autonomous secrets rollover in a distributed computing environment. In various embodiments, dSMS can autonomously rollover client certificates for authentication of users who access a security critical service, autonomously rollover storage account keys, track the delivery of updated secrets to secrets recipients, autonomously rollover secrets for services sharing secrets with other services across regional or other scope boundaries, deliver secrets to a service application using a secure blob, and/or facilitate autonomous rollover using secrets staging.

In this manner, techniques disclosed herein improve upon conventional systems in various ways. For example, a secrets management service can facilitate a fully autonomous secrets rollover, rotating secrets through a distributed environment in a more efficient manner than conventional systems, and without requiring manual orchestration. For example, a service model and/or corresponding configuration file does not need to be updated, and autonomous secrets rollover can occur without redeploying the services which use the secrets, thereby avoiding outages and security non-compliances resulting from conventional practices. Various aspects described herein provide novel or otherwise improved functionality, including the ability to track rollover progress, provide autonomous cross-scope rollovers without service interruption, deliver secrets using a secure delivery mechanism, and provide a phased rollover of new secrets by validating usage of new secrets prior to a full rollover across all services. As such, using techniques described herein, rollover and expiration of secrets are more predictable than conventional systems, and unlike conventional systems, rollover can be performed without service disruption within a distributed computing environment.

Datacenter Secrets Management Service (dSMS)

With reference to FIG. 1, embodiments of the present disclosure can be implemented in a distributed computing environment (e.g., example distributed computing environment 1600 in FIG. 16) which facilitates autonomous secrets renewal and/or distribution. In the embodiment illustrated in FIG. 1, autonomous secrets management system 100 includes front end 105, data center secrets management service (“dSMS”) 110, certificate authority (“CA”) 115, fabric controller 120, and node 130 with virtual machine (“VM”) 145. Node 130 includes host agent 135 and credentials management host agent plug-in 140, and VM 145 includes guest agent 150 and credentials management service 155. Autonomous secrets management system 100 further includes data center secret token service (“dSTS”) 160, onboarding service 165, managed service 170, client device 175, and temporary shared access signatures (SAS) service 180. Some of the components of autonomous secrets management system 100 can correspond to components in example distributed computing environment 1600 in FIG. 16. Likewise, autonomous secrets management system 100, or aspects thereof, may be implemented using one or more computing devices such as computing device 1700 of FIG. 17. The components of autonomous secrets management system 100 may communicate with each other via a network, which may include, without limitation, one or more local area networks (LANs) and/or wide area networks (WANs). Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.

Generally, a client may configure a service model via front end 105 to deploy a desired service. Front end 105 operates as a service end point for the distributed computing environment. Previously, the client could define secrets to be used by the service, and the service model (e.g., a configuration file of the model) was generated that referenced a particular version of a secret (e.g., a certificate thumbprint). Once a service instance was deployed (e.g., the service model was distributed), the service was pinned to the particular version of the secret manually specified in the service model. If the secret expired or got revoked, the client had to manually renew the secret, provide the renewed secret, update the configuration model, and redeploy each service that relied on the secret (issuing new deployments to push them all down). Such conventional techniques required significant human intervention, which can be time consuming, inefficient, and susceptible to human error.

As such, techniques disclosed herein can implement autonomous secrets rollover such that a client need only initially configure a desired service and specify a secrets rollover policy, after which a secrets management service can autonomously rollover the secrets. Additionally and/or alternatively, techniques disclosed herein can utilize an alternative structure in which a service (e.g., a service model and/or corresponding configuration file) references a location for a secret (e.g., a path) instead of a particular version (e.g., thumbprint). As used herein, this is referred to as pinning the service to location or path. When a secret is renewed, the location or path does not change. As such, the service model and/or corresponding configuration file does not need to be updated, and autonomous secrets rollover can occur without redeploying the services which use the secrets.

In the embodiment illustrated in FIG. 1, a client can configure a particular distributed computing service via front end 105. The configuration can include specifying secrets and a secrets rollover policy (e.g., timing for renewals, dependent services, timing for distribution of renewed secrets, staging, cross-scope applicability, etc.). A service model and/or configuration file can be generated referencing secrets by the path (e.g., absolute, relative, etc.) at which they are stored. For example, dSMS 110 can store secrets in secrets store (“SS”) 113, so the referenced secrets path can be the directory of secrets store 113. Advantageously, dSMS 110 is implemented using Representation State Transfer (“REST”) communications protocol to facilitate inferring the directory of the secrets store from the system architecture. For example, in embodiments with one dSMS per region (e.g., US West), the US West secrets store can be assigned as the secrets store for tenants with a home location in US West. By implementing REST, the absolute path of a secret need not be specified in a service model and/or configuration file because it can be inferred based on the tenant's home location. As such, implementing REST can simplify system communications. Other variations and combinations of representations of the path are contemplated with embodiments described herein.

Generally, dSMS 110 is a secrets management service which can be deployed in a distributed computing environment and that generally orchestrates the autonomous secrets rollover. As used herein, secrets rollover comprises secrets renewal and distribution. Generally, a secret may be initially provided to dSMS 110, which installs and initially deploys the secret. As used herein, installing a secret refers to storing or otherwise making the secret accessible to support authentication operations. For example, dSMS 110 may store secrets in secrets store 113, including certificates (e.g., chained, self-signed, imported, etc.), storage account keys, shared access signatures (“SAS”), connection strings, custom types, and/or the like. Generally, secrets are associated with a service resource (e.g., a particular storage blob, service principal object, connection string, etc.). Additionally and/or alternatively, secrets can be associated with a deployment identification (e.g., <Fabric DNS, Tenant Name> tuple). In some embodiments, dSMS 110 pushes secrets to fabric controller 120 which caches them in secrets store 123. A push model can be beneficial to the extent it removes dSMS 110 from critical workflows in fabric. During an initial deployment, fabric controller 120 can deploy the specified secrets to corresponding VMs and/or nodes (e.g., to start an instance). When a secret managed by dSMS 110 is up for renewal (e.g., based on the specified renewal policy, based on a requested on-demand rollover, etc.), dSMS 110 can automatically renew the secret (e.g., by issuing a new version of the secret, such as a self-signed certificate, by requesting a new version of the secret from an external authority, such as certificate authority 115, by requesting or otherwise accessing a new version of a secret, etc.). New versions of secrets such as SSL/TLS certificates can be automatically linked to prior versions (e.g., using Schannel linking) to avoid the need to re-bind and/or reboot. Renewed secrets are stored at the designated path for each secret, pushed to fabric controller 120 for caching in secrets store 123, and fetched by corresponding VMs and/or nodes. In this manner, dSMS 110 facilitates a fully autonomous secrets rollover.

In some embodiments, dSMS 110 can generate service objects to encapsulate information about secrets, secrets versions, and secrets deployments. Service objects define the services which use dSMS. Service objects generally include a list of secrets which will be used by a deployed service and a list of deployment information. Deployment information can specify where the secrets are deployed (e.g., cluster, tenant), the identity certificate for a corresponding service agent, an internal state of fabric controller 120 for tracking which versions of secrets have been installed there, and/or whether secrets installed on an agent are up to date. dSMS 110 can generate, update and otherwise manage corresponding service objects during various stages of operation, including onboarding, deployment, secret rollover, and/or reconciliation with the fabric. For example, during onboarding, a client registers with dSMS 110 by specifying secrets and a secrets rollover policy for a particular service, and dSMS 110 creates a corresponding service object for the service. During deployment, dSMS 110 contacts fabric controller 120 and pushes the secrets referenced in a corresponding service object to secrets store 123. During a secret rollover, dSMS 110 can refer to a service object to lookup and/or update the internal state of fabric controller 120 to reflect whether the renewed secret has been pushed to fabric and/or confirmed. In some embodiments, fabric controller 120 can poll dSMS 110 for updates and provide an indication of its internal state. If dSMS 110 recognizes an internal state that is different from the state recorded in a corresponding service object, dSMS 110 can respond with updates.

In some embodiments, dSMS 110 can provide a data feed providing access to metadata about secrets. For example, a compliance auditor may use the data feed to verify secrets are in compliance. Additionally and/or alternatively, the data feed can be leveraged as a part of an external auto-renewal process. For example, an external agent can interrogate dSMS 110 via the data feed to monitor for an approaching expiration, which can trigger a workflow to renew and push a secret to dSMS 110. This configuration is merely one example, and other variations will be understood by those of ordinary skill in the art.

Returning now to autonomous secrets management system 100, the components of autonomous secrets management system 100 may be configured to facilitate any or all of the techniques described herein. For example, some or all of the components can be configured to reference secrets using their path at which they are stored. As another example, secrets store 123 of fabric controller 120 can serve as a cache for secrets managed by dSMS 110. Generally, dSMS 110 can push secrets to the fabric during an initial deployment. Subsequently, any time a secret is renewed, dSMS 110 can update the secret in secrets store 123 of fabric controller 120. This way, secrets store 123 of fabric controller 120 can be used as a reference for version control, removing dSMS from service healing processes. For example, if VM 145 goes bad during a rollover, but before the VM's cached secrets have been updated, host agent 135 can interrogate secrets store 123 as part of the self-healing process, instead of issuing a request to dSMS 110, to ensure regeneration occurs using the latest secrets cached in secrets store 123.

On the node side, when an agent of node 130 (e.g., host agent 135, guest agent 150, etc.) receives managed secrets, it can install the secrets on a corresponding secrets store (optionally subject to staging, as discussed in more detail below). A credentials management component (e.g., credentials management host agent plug-in 140, credentials management service 155, etc.) can coordinate updates on node 130. For example, the credentials management component can periodically poll dSMS 110 using a defined polling interval (e.g., once a day) for updates. The poll can include metadata identifying the deployment and/or the current version of the secrets on node 130. In the event renewed secrets are available, dSMS 110 replies with the renewed secrets, and the credentials management component installs them.

Turning now to FIG. 2, FIG. 2 illustrates example process flows through example autonomous secrets management system 200. In this embodiment, autonomous secrets management system 200 includes dSMS 210, fabric controller 220, and node 230. Node 230 includes agent 240, secrets store 250, and credentials management component 260. An example service deployment is indicated in FIG. 2 by Arabic numerals 1, 2, and 3. An example secret renewal is indicated in FIG. 2 by Roman numerals I, II, and III. For example, during an initial deployment of a particular service, dSMS 230 pushes the secrets for the service to fabric controller 220, which starts a corresponding role for the service and provides a secrets package to agent 240. Agent 240 installs the secrets in secrets store 250 for use by the service. During a secrets renewal, dSMS 210 generates, requests, or otherwise accesses a renewed secret and pushes the renewed secret to fabric controller 220. Meanwhile, credentials management component 260 periodically polls dSMS 210 for renewed secrets. When a renewed secret is available, dSMS 210 provides the secret to credentials management component 260, which installs the secret in secrets store 250.

As such, an autonomous secrets management system can be provided which automates secrets lifecycle management, including autonomous renewal and/or distribution of secrets. By configuring a service to reference the location of a particular secret, autonomous renewal can occur without redeploying the service. As such, an autonomous secrets management system can be provided that performs autonomous rollover of secrets without manual redeployments and/or service interruptions.

Automatic Updates of Client Certificates

Generally, a client calling into a service (e.g., on a server and/or in a distributed computing environment) can authenticate in various ways, including using certificates. When a certificate gets updated (e.g., version 1 to version 2), the new version will have a different thumbprint. If the certificate is updated for only one of the client and service, authentication will fail. As such, in some embodiments, a secrets management service (e.g., dSMS 110, 210, 310, 410, 435, 445, 455, 510, etc.) can be utilized to autonomously rollover client certificates for authentication of users who access a security critical service. FIG. 3 illustrates example autonomous client certificate management system 300, in accordance with embodiments described herein. Autonomous client certificate management system 300 includes dSMS 310, certificate authority 320, client app 330, service app 340, and whitelist 350. Generally, dSMS 310 can correspond to dSMS 110 and/or dSMS 210 of FIGS. 1 and 2, respectively.

Generally, client app 330 is onboarded into dSMS 310, so required certificates (e.g., the client certificate “CER”) can be initially deployed into client app 310. Client app 330 and/or service app 340 can fetch renewed certificates using the polling technique described above. Service app 340 can be deployed using any mechanism, and generally whitelists client certificates in whitelist 350. To accomplish this, service app 340 is provided with the CER and its corresponding location in dSMS 310. When client app 330 connects to service app 340 (e.g., in a TLS session), client app 330 presents the latest copy of the CER to service app 340. Service app 340 checks whitelist 350, and if the CER is in the whitelist, validation succeeds. Otherwise client certificate validation fails, and an incident alert may be issued.

Various fallback techniques can be applied in the event client certificate validation fails. For example, in some embodiments, dSMS 310 generates and distributes multiple versions of secrets, such as client certificates (e.g., in a vector). By way of non-limiting example, dSMS 310 can package and distribute three versions of certificates. Additionally and/or alternatively, secrets recipients can maintain a cache of prior versions instead of deleting them. As such, in the event client certificate validation fails, client app 330 can retry with a prior version of the CER. In another example, if validation fails, service app 340 can poll dSMS 310 for any updates to the secrets stored in whitelist 350 (e.g., an updated CER).

Advantageously, service app 350 can include a worker thread which periodically polls dSMS 310 for updated public information. Since the request is for public information, the request can be an anonymous call to a public end point of dSMS 310. The worker thread can be packaged as a shared library (e.g., MICROSOFT's dynamic link library (“DLL”)) for service app 340 to consume. By packing the polling logic into a DLL, dSMS 310 can control a back-off strategy for polling requests and/or updates to the polling API. Additionally and/or alternatively, when dSMS 310 renews a secret (e.g., the CER), dSMS 310 can distribute the renewed secret to client 330 via a trusted end point of dSMS 310 subject to a secrets release delay. A secrets release delay waits for a configurable time period releasing and/or delivering the renewed private key to client app 330, while advertising the renewed public key to service app 340. In this manner, a secrets release delay can provide service app 340 with time to poll dSMS 310 to pick up the renewed CER before dSMS 310 releases the renewed CER to client app 330.

In this manner, dSMS can be utilized to autonomously rollover client certificates for authentication of users who access a security critical service.

Automatic Rollover of Storage Account Keys

In some embodiments, a secrets management service (e.g., dSMS 110, 210, 310, 410, 435, 445, 455, 510, etc.) can be utilized to autonomously rollover storage account keys. Generally, storage account keys utilize primary and secondary keys. A given key has a designated lifecycle, and the continued use of a key after its designated lifecycle would be noncompliant. Rolling over storage account keys and/or SASes involves considerations involving these primary and secondary keys.

For example, in some embodiments, primary and secondary keys for a storage account are rolled over on a predefined schedule in an interleaving fashion. More specifically, the expiration of the primary key is arranged to be separate from the expiration of the secondary key. A customer can specify the renewal period in dSMS, for example, when onboarding into the dSMS. In an example in which keys have a two year expiration, every year either the primary or the secondary key is renewed and distributed. In some embodiments, timer workers can be used to autonomously renew storage account keys.

Any SASes which depend upon a storage account key can be generated and/or rolled over based on the expirations of the storage account keys. For example, dSMS can define an active key as the key which has farther expiration (i.e. the key which is valid for the longer period of time). As such, dSMS can generate any SASes using the active key. Moreover, any SASes which depend upon a storage account key can be rolled over prior to rolling over the key upon which they depend. For example, if a first storage account key is being rolled over, dSMS can regenerate any dependent SASes using the other key prior to rolling over the first key. In some embodiments, timer workers can be used to autonomously renew storage account keys and/or autonomously regenerate SASes.

In this manner, a secrets management service such as dSMS can be utilized to autonomously rollover storage account keys. As such, rollover and expiration are predictable, and rollover can be performed without breaking a communication scheme.

Secrets State Tracking

Generally, secrets can be associated with deployments (e.g., deployment location). Sometimes, a particular service object can be associated with multiple deployment locations (e.g., for redundancy). As such, sometimes a particular secret can be associated with multiple deployment locations. In some embodiments, a secrets management service (e.g., dSMS 110, 210, 310, 410, 435, 445, 455, 510, etc.) can track the delivery of updated secrets to each associated deployment location. For each secret, dSMS can track its status across all nodes and/or agents in the fleet for a particular location or service object. For example, dSMS can track the internal state of each of each node and/or agent in fabric and update it whenever the node/agent polls. This way, dSMS can track the entire rollover progress of secrets and fire off desired alerts.

In some embodiments, dSMS can create and maintain a state tracker for secrets recipients. For example, an agent state tracker can be a repository for the state of agents at each of the deployment locations. Various states can be tracked (e.g., secret not delivered, secret delivered, secret confirmed) for each instance, and the states can be encoded for storage (e.g., 0, 1, 2). In some embodiments, the last time an agent polled dSMS can be tracked. Generally, polling can include metadata identifying the deployment and/or secrets metadata identifying the current version of the secrets used by the instance and/or their path. As such, if an agent and/or an associated polling component (e.g., credentials management host agent plug-in 140, credentials management service 155, credentials management component 260, a polling component of client app 330 and/or service app 340, a polling component of US West 430, US East 440 and/or Japan 450, credentials management service 530, etc.) polls with an incorrect state (e.g., dSMS delivered a renewed secret and expected a confirmation, but the agent polled with the prior secrets version), dSMS can resubmit the renewed secret to the agent. Since polling occurs periodically, in some embodiments, the state tracker for secrets recipients need not be backed up, since it can be reconstituted from polling requests that indicate an agent's internal state.

In some embodiments, dSMS can create and maintain a state tracker to track the progress of a particular rollover. This state tracker can also be thought of as a dSMS state tracker. Advantageously, a separate repository is created for maintaining the agent states than for maintaining the dSMS state to prevent locking the dSMS repository at a higher rate, hence making it more available for other management operations. For each secret, dSMS can track the secret's expiration, last poll, next poll, and rollover state (e.g., rollover started, rollover completed), which can be encoded for storage (e.g., 0, 1). In one example, dSMS can create a goal state corresponding to a successful rollover (e.g., rollover completed) and/or dSMS can set the current dSMS state to “rollover started” after a successful push to the fabric and/or once dSMS releases the secret to the polling agents. Once delivery of a renewed secret to each agent for a particular service has been confirmed (e.g., the agent state tracker indicates a corresponding confirmed state for each agent), dSMS can move the current dSMS state to the goal state (e.g., “rollover completed”). More specifically, a worker thread can monitor the agent state tracker to identify when all the role instances have a secrets confirmed state. The worker thread can then update the dSMS state to indicate the rollover is complete, and can delete the corresponding records from the agent state tracker.

In this manner, dSMS can track rollover progress and fire off desired alerts. More specifically, the use of one or more state trackers can be used to drive alerts and/or triggers. For example, dSMS can generate a warning that a rollover previously began but has not completed within some predetermined amount of time (e.g., within 2 months of beginning the rollover, before 30 days prior to expiration, etc.). Similarly, dSMS can provide a notification to a customer when a rollover starts in order to trigger a customer workflow (e.g., a manual update, a secrets release delay, etc.). Additionally and/or alternatively, a data feed of dSMS can be interrogated to permit a process to monitor or otherwise check one or more of the state trackers, for example, to provide a warning, trigger a workflow, and the like.

Cross-Scope Secrets Management

There are several scenarios in which it may be desirable for services to share secrets. For example, when redundancy is desired across regions, in case one region (or its dSMS) goes down, the secrets can be backed up in redundant region. As such, in scenarios operating independent data centers in multiple regions, each data center can include its own dSMS. In this case, the redundant services and/or dSMSes should share secrets. In another example of sharing secrets, some clients may need to connect services across regions, so authenticating such services can involve shared secrets.

When services that need to share secrets are not in the same replication scope, various problems can arise in conventional systems. As explained above, when distributed secrets are renewed, there is no conventional mechanism to automatically rollover updates. This can cause issues, for example, when a manual rollover is not completed before a secret expires (e.g., system outage, non-compliance, etc.). In another example, some cross-scope architectures require rotating storage account keys. However, when storage account keys are rotated, the old key becomes invalid. Without a mechanism to automatically rollover updates, rotating a storage account key in one replication scope can break a cross-scope communication scheme. As such, there is a need for a broker to orchestrate the sharing of secrets across scopes to ensure.

Accordingly, in some embodiments, a cross-scope secrets management service, such as dSMS, can be utilized to orchestrate cross-scope secrets rollover. A dSMS may be provided in each scope (e.g., each region) utilized by a service. To orchestrate secrets renewal and distribute across scope boundaries, a cross-scope dSMS can be deployed in an arbitrary scope. During an initial deployment, a customer onboards secrets with a cross-scope dSMS, registering cross-scope secrets and their desired availability across scopes (e.g., replication scope). The cross-scope dSMS can store the secrets, and the secrets can be referenced by their path in the cross-scope dSMS. Similarly, the customer onboards the secrets with each local dSMS by registering the cross-scope secrets and providing their location (e.g., their path in the cross-scope dSMS). In this manner, each local dSMS subscribes to receive updates from the cross-scope dSMS. As secrets are renewed, they are automatically propagated to the subscribing local dSMS and distributed within the local scope by the local dSMS (e.g., using the polling technique described above).

Generally, the cross-scope dSMS can orchestrate a cross-scope rollover (e.g., a global rollover). A cross-scope rollover can occur autonomously according to a defined secrets rollover policy and/or in response to a manual rollover request. For example, the cross-scope dSMS can automatically rollover secrets, as described above, and each local dSMS can periodically poll for updates. Additionally and/or alternatively, a rollover request can be received at the cross-scope dSMS and/or any local dSMS. In some embodiments, a rollover request received at a local (e.g., regional) dSMS can trigger an on-demand fetch request to obtain the most recent secret from the cross-scope dSMS. In the event a renewed secret is available, the local dSMSes can sync the newer version from the cross-scope dSMS, update its own copy, and distribute within its corresponding local scope.

FIG. 4 depicts example autonomous cross-scope secrets management system 400. In this example, customer 420 onboards shared secrets with cross-scope dSMS 410 in US Central 405 Likewise, customer 420 onboards shared secrets with local dSMSes 435, 445, and 455 in US West 430, US East 440, and Japan 450, respectively. In some embodiments, customer 420 provides an initial copy of a shared secret to local dSMSes 435, 445, and 455 when onboarding. Additionally and/or alternatively, local dSMSes 435, 445, and 455 can fetch initial copies of shared secret from cross-scope dSMS 410 (e.g., during onboarding, periodic polling, etc.). When cross-scope dSMS renews a secret, local dSMSes 435, 445, and 455 pick up the renewed secret (e.g., during periodical polling) and distribute the renewed secrets within their corresponding local scopes.

In some scenarios, a local dSMS may not have the latest copy of a shared secret. Generally, state tracking can be performed across the composite cross-scope and local dSMSes to facilitate autonomous cross-scope rollovers without service interruption. For example, each local dSMS can track its own local rollover, while the cross-scope dSMS tracks a cross-scope rollover. Additionally and/or alternatively, the cross-scope dSMS can track local and cross-scope rollovers. If a cross-scope rollover has begun, but a local dSMS does not have the latest copy of a shared secret, the local dSMS may respond differently depending on the type of secret in question. For example, a local dSMS may continue using a prior version of a certificate/managed service identity until receiving a renewed version. However, for storage accounts, since a rolled over key in the cross-scope dSMS will invalidate a prior copy in a local dSMS, the local dSMS can fall back to an alternative key. For SASes, since a rolled over SAS token in the cross-scope dSMS will invalidate a prior copy in a local dSMS, a local application can trigger an on-demand fetch request for a renewed token from the cross-scope dSMS, which can trigger a corresponding local rollover. Other examples will be understood by those of ordinary skill in the art.

As such, services can share secrets across scope boundaries utilizing a cross-scope secrets management service such as dSMS to orchestrate cross-scope secrets rollover.

Delivery of Secrets as a Secure Blob

In some embodiments, a secrets management service (e.g., dSMS 110, 210, 310, 410, 435, 445, 455, 510, etc.) can deliver secrets to a service application using a secure blob. For example, dSMS can deliver secrets packaged in a secure blob to a service application co-hosted with other services in a distributed computing environment.

Generally, secrets required by a service can be grouped into a secrets package and delivered to various components in a secure manner. A secrets package includes a secure blob serving as a container for one or more of the service's secrets. The secrets package optionally includes one or more additional secrets such as a certificates outside of the blob. The secrets package and/or secure blob can be associated with the service and/or a corresponding role. Generally, a secure blob is an opaque byte array that may be extensible using a data serialization framework such as Bond. dSMS can package one or more managed secrets into a secure blob for distribution. For example, dSMS can package all secrets for a particular service, or some portion thereof, into a secure blob. Since the contents of the secure blob are generally invisible to components of a distribution pipeline, in some embodiments, one or more additional secrets for a service (e.g., certificates) can be included in the secrets package outside of the secure blob to facilitate use of those secrets by one or more components of the distribution pipeline and/or a distributed computing environment (e.g., binding a certificate to a particular endpoint). Advantageously, the secure blob is encrypted during transport (e.g., using the target machine's public key) and stored encrypted.

A secrets package may be used to distribute secrets, as described herein. For example, when a customer onboards secrets and associates them with a service object, dSMS may generate a secrets package and push the secrets package to fabric, and fabric can store the secrets and initially deploy them. Additionally and/or alternatively, dSMS may initially push certificates, after which it may generate and push a secure blob with the rest of the secrets for the service. In this scenario, fabric may initially deploy the secrets package and/or separately deploy the secure blob. For example, where a secrets package includes certificates that are not packaged in the secure blob, and the fabric deploys the secrets package to a node, an agent on the node can install the unpackaged certificates and save the secure blob to disk. As such, the secrets can be read by the service and/or a credential management component.

In some embodiments, the service object, the secrets package, and/or the secure blob can be version controlled (e.g., using entity tags (“ETag”)). When a secret is renewed, a new secrets package and/or secure blob can be generated, the version on the secrets package, secure blob, and/or a corresponding service object can be updated, and the new secrets package and/or secure blob can be pushed to fabric. When an agent polls dSMS to check for renewed secrets, the agent can include secrets metadata indicting its current secrets version. dSMS can compare the version indicated by a polling request with the latest version (e.g., for the secrets package, secure blob, and/or a corresponding service object), and if the agent needs an update, dSMS can reply to the agent with the latest secrets package and/or secure blob.

As such, a secure blob can be used to deliver periodically refreshed secrets as they change.

Secret Staging

Depending on the nature of a secret, applications which make use of the secret may require an orchestrated rollover across a service. As such, in some embodiments, autonomous secrets rollover includes secret staging. Generally, services may be customized to stage and/or synchronize deployment of renewed secrets among their role instances. Such orchestration can be achieved by a staging mechanism implemented on a client, a service (e.g., dSMS), or both.

In a client-side staging model, a secrets management service (e.g., dSMS 110, 210, 310, 410, 435, 445, 455, 510, etc.) releases renewed secrets to a container, and the secrets are securely cached in a staged mode. A corresponding application and/or an external orchestration engine can determine when to begin using the secret, and can trigger the unstaging of the secret for active use. Client side staging may be specified by a customer (e.g., during onboarding), and may be applied selectively to designated secrets. FIG. 5 depicts an example autonomous secrets management system with staging.

In FIG. 5, autonomous secrets management system 500 includes dSMS 510, fabric controller 520, credentials management service 530, role 540, secrets store 560, and orchestration engine 550. In this embodiment, when dSMS 510 automatically renews a secret, it pushes the renewed secret to fabric controller 520 and releases the renewed secret to credentials management service 530. Credentials management service 530 picks up the renewed secret during the course of periodically polling dSMS 510. In this example, once credentials management service 530 receives a renewed secret, it caches the staged secret and waits for authorization to use the renewed secret. Generally, credentials management service 530 can cache the renewed secret by installing it at the same location as the prior secret with a property designating the secret's status as staged. In some embodiments, renewed certificates can be stored in the same location as the prior certificate without linking the renewed certificate to the prior version.

Various mechanisms can be utilized to evaluate and control when to unstage a cached secret. In one example, a local application can implement a desired staging routine. In another example in the embodiment depicted in FIG. 5, an external component is used to facilitate unstaging. More specifically, credentials management service 530 notifies role 540 that a renewed secret is available, and role 540 requests a lease to renew the secret from orchestration engine 550. Generally, orchestration engine 550 can determine when it is safe for a role to accept a renewed secret. For example, orchestration engine 550 may be in communication with multiple nodes and/or roles for a service in order to orchestrate a rollover within a service. For example, orchestration engine 550 may implement logic to update one node at a time (e.g., round robin, some other update scheduling, etc.). Generally, orchestration 550 can authorize role 540 to unstage a renewed secret (e.g., by granting it a lease to unstage the secret), upon which role 540 can accept the renewed secret by removing the staged property from the cached secret. For example, role 540 may call a method of credentials management service 530 that accepts the renewed secret in secrets store 560. In some embodiments, role 540 can be notified that the installation has occurred.

Additionally and/or alternatively, once orchestration 550 authorizes role 540 to unstage a renewed secret (e.g., by granting it a lease to unstage the secret), orchestration engine 550 may be capable of monitoring role 540 for some predetermined period of time (e.g., 24 hours) to determine a measure of the health of the role. For example, orchestration engine 550 may monitor health signals (e.g., CPU usage), authentication failures, and the like. In the event orchestration engine 550 determines that role is healthy and/or the renewed secret was unstaged successfully, orchestration engine 550 can apply the renewed secret to subsequent roles.

In a service side-staging model, a secrets management service such as dSMS can rotate secrets according to a defined rollover policy, but defer releasing renewed secrets to all nodes of a tenant (or application) at once. Instead, dSMS can release secrets to one update domain at a time and wait for feedback from application services deployed in the update domain prior to moving to the next update domain.

In this manner, staging allows a phased rollover of new secrets by validating usage of new secrets prior to a full rollover across all services.

Managed Service Identity

In some embodiments, dSMS (e.g., dSMS 110) provides support for autonomous secrets management for a managed service identity (e.g., identity of managed service 170). By way of background, any subject can identify itself with an identity provider (e.g., dSTS 160) using several different mechanisms (e.g., certificate/private key). For example, a user account could exist on a dSTS, where dSTS has a public key corresponding to the private key. The subject communicates with dSTS and indicates that it has the private key and requests a token. The dSTS provides the token and user account information for a subject.

As mentioned, the subject can be a service having an identity. In particular, the service is associated with an identity in order to communicate with other services. For example, a frontend service, for a frontend portal, can communicate with a backend service; however only after the identity of the frontend service has been authenticated. Both services can communicate with each other based on a common trust in dSTS, the dSTS provides both their identities and private keys, such that each service trusts the other service. Services have to periodically rotate their private keys (e.g., for security and compliance purposes), which currently in conventional systems is performed manually. For example, conventionally, a service would be pinned (e.g., via a front end 105) to a thumbprint of a certificate, and the service would reach out to retrieve a token from the dSTS based on the pinned thumbprint. Further, conventionally, manually pinned certificates have to be manually rolled over, which can be tedious and challenging, as discussed herein in detail above.

Autonomous secrets management for a managed service provides for using the identity name of a managed service to retrieve a token from a dSTS, and also includes autonomous secrets renewal and distribution of secrets for the managed service operating with the dSTS. In this regard, the managed service can be authenticated for performing operations with other services, while delegating operations of secrets management to dSMS. At a high level, a managed service uses its identity name to retrieve a security token operating in collaboration dSMS 110, to allow dSMS to manage secrets. The managed service and the dSMS can both support operations (e.g., via APIs) that allow for processing managed service retrieval of a token from dSTS. In operation, by way of example, an onboarding service (e.g., onboarding service 165) can communicate with dSTS to create a user account for the managed service. The user account can include claims on for the user account. For example, a user account for a managed service identity can include a claim, where the claim is a statement that a subject makes about itself or another subject. The statement can be about a name, identity, key, group, privilege, or capability, for example. Claims can be issued and given one or more values and then packaged in security tokens that are issued by the dSTS.

The secrets (e.g., MSI certificate) can be created on dSMS with a dSTS deployment location. The dSMS can create dSTS deployment tasks. For example, the dSMS can instruct the dSTS to set the certificate credentials on the dSTS. dSMS can call a corresponding task API (e.g., SetCredentials API) on dSTS which allows setting performing the task (e.g., setting of certificate credentials for a user account on dSTS). dSMS can communicate with the onboarding service any task details or acknowledgement of completion of creation of the MSI certificate.

In some embodiments, the dSMS can create a self-signed certificate for the MSI. Upon completing dSTS deployment tasks, the MSI certificate may be deployed. In operation, the onboarding service can also instruct the dSMS to create a self-signed managed service identity (“MSI”) certificate (i.e., private key). MSI is the identity that corresponds to the managed service. The MSI is associated with a private key and public key, the public key is communicated to the dSTS. The public key of the MSI is stored on the dSTS with the private key on the dSMS. As discussed herein, a frontend can be used to deploy a service. For example, a service object is created with the fabric and tenant information. An MSI secret (e.g., certificate) can be read from the service model and the secret is added to the service object. The secret is then pushed to the computing fabric. The onboarding service can operate as a resource manager to support additional operations to enable the managed service for requesting for tokens, via a credentials manager, from the dSTS in order to have additional secrets management performed using the dSMS. In particular, the credentials manager (e.g., credentials management service 145) can operate to retrieve the token from the dSTS. In operation, the managed service can communicate its identity name (e.g., identity identifier) to the credentials manager that then retrieves a secret associated with the managed service based on a mapping between the managed service and the secret at the credentials manager. The credentials manager can then use the identified secret to retrieve a token from dSTS.

Additional operations can be supported for autonomous secrets management with an onboarding service, dSMS and dSTS operating in collaboration. For example, secret rollover operations, secret revocation operations, and secret removal operations, having corresponding rules, can each be performed based on an ordered combination of steps. The rollover operation or process can be configured to fail is any previous deployment tasks have not been completed. In some embodiments, a new version of a secret (e.g., MSI certificate) is self-signed when created. The rollover operation can also include transmitting the credentials to the dSTS. In operation, dSMS makes a determination that a rollover is needed. dSMS then determines that no deployment tasks as active, such that when no deployment tasks are active, dSMS creates new deployment tasks for the new secret. As before, credentials for the secret are transmitted to the dSTS. Upon determining the MSI certificate is ready for deployment, the MSI certificate is transmitted to the computing fabric.

A secret removal operation can include dSMS determining that, for a service object, there exist no accounts reference the service object (e.g., secret/MSI certificate). dSMS then instructs the dSTS to delete the user account information. dSMS can also validate whether there are any user accounts for a secret on the dSTS before removing the MSI certificate. If the user account is present the MSI certificate will not be deleted. dSTS can be configured to support immediate revocation operations using a revocation list, where a certificate is added to a revocation list when it is determined that the certificate could cause a service outage. Rollover operations are performed via the dSMS and the certificate is rolled over. The new certificate is added to dSTS and pushed out to the service. Delayed revocation operations can include the dSMS performing rollover operations immediately, bypassing the revocation list, and placing the certificate in the revocation list after the dSMS has added the certificate to dSTS and pushed out to the fabric.

In an exemplary implementation, the managed service includes code that requests the access token, where the code does not have to include the secret or any other credentials except for the identity identifier of the managed service. The code can include an abstraction of the managed service identity so that the credentials manager that has access to the secret store of the secret of the managed service, and the credentials manager is delegated to retrieve the token. The credentials manager can support multiple services and multiple dSTSs. For example, the code can include the identity identifier and additional metadata that support identifying the corresponding dSTS. The credentials manager matches the identity name of the service to locally store credentials and uses the credentials to retrieve, from the dSTS, a token on behalf of the managed service. The credentials manager can have a mapping file, database, or data structure that supports determining the corresponding secret/secret location and dST for a managed service, such that the credentials manager retrieves and communicates the token to the managed service. The managed service can then use the token to authenticate with dSTS. Accordingly, the managed service may operate primarily based on its identity name to retrieve a token with direct access to a secret (e.g., certificate). dSMS in turn provides autonomous secret management as described herein.

Accordingly, a method for managing secrets includes generating, at a managed service, a first token request for a token. The token supports authenticating the managed service in a distributed computing environment. The first token request comprises an identity identifier of the managed service, where the token is retrievable based on a secret that is associated with a secrets management service (“SMS”) for autonomous management of the secret. The secret is pushed to a secret store, corresponding to the credentials manager, during initial deployment of the managed service to a computing fabric. Secrets management includes periodically polling the SMS for an automatically renewed version of the secret by providing the SMS with metadata indicating a current version of the secret on a node running the managed service. The SMS is configured to deliver the secret packaged in a secure blob, where the secure blob is an opaque byte array containing the secret.

Generating the first token request obviates including a secret in the first token request, where the first token request is communicated as a local request to the credentials manager on a node running the managed service. The first token request further comprises metadata that supports identifying secret token services that correspond to managed services, or a virtual machine running corresponding managed services, or a node running corresponding managed services. The method also includes communicating the first token request to a credentials manager. The method further includes, based on communicating the first token request to the credentials manager, receiving the token, from a secret token service, wherein the token is received based in part on the credentials manager generating a second token request for the token and communicating the second token request and the secret associated with the managed service to the secret token service.

In another embodiment, managing secrets includes receiving, from a managed service, a first token request for a token. The token supports authenticating a managed service for performing operations in a distributed computing environment. The first token request comprises an identity identifier of the managed service. The first token request further comprises metadata that supports identifying secret token services that correspond to managed services, or a virtual machine running corresponding managed services, or a node running corresponding managed services. The first token request excludes the secret in the first token request. The method further includes based on the identity identifier, identifying a secret for the managed service. A secret management service (“SMS”) operates to automatically renew secrets. Identifying the secret for the managed service based on a mapping between identity identifiers and secrets in a secrets store, wherein the identity identifiers and secrets further map to corresponding secret token services. The method also includes determining a secret token service associated with the identity identifier; communicating, to the secret token service, a second token request comprising a secret; receiving the token from the secret token service; and communicating the token to the managed service.

Temporary SAS Service

In some embodiments, dSMS (e.g., dSMS 110) provides support for autonomous secrets management for a temporary SAS service. By way of background, a temporary SAS service (e.g., dSAS 180) in a distributed computing system operates to manage temporary access to resources. For example, a developer supporting a cloud service or application may not have persistent access to a restricted resource, thus the dSAS processes a temporary access request, based on a user access policy, and provides appropriate access to the restricted resource. Access to the resource can, in particular, be limited to a certain level or type of access, and also limited in time such that the access is revoked when a time period expires. In particular, a shared access signature allows a subscriber to a distributed computing system to grant limited access to objects in their storage account to other clients, without exposing an account key. In this regard, the SAS provides delegated access to the storage account. A client (e.g., client device 175), that needs temporary access to a storage account, may be authenticated via an identity provider (e.g., dSTS 160) and receive a SAS, so that the client device can access a storage account resource directly with the permissions defined by the SAS and for the interval allowed by the SAS. The SAS mitigates the need for routing all data through a front-end proxy service.

In this regard, dSAS operates to manage access to a subscriber's storage accounts and master keys. However, conventional temporary SAS services have to manage rolling over of primary keys and SAS keys when providing temporary access. Rolling over storage account keys and/or SASes involves considerations for these primary and secondary keys. Autonomous secrets management for a temporary SAS service includes, first, using a storage account validation function executed against a dSMS to validate a temporary access request, and, secondly, receving a SAS key, based on validating the temporary access request, to gain temporary access to the storage account. In this regard, the temporary SAS service can provide temporary access to a storage account while delegating at least some operation of secrets management to dSMS.

At a high level, the dSAS, supports delegating access to resources of a storage account in collaboration with dSMS 110, to allow dSMS to manage secrets. The dSAS and dSMS can both support operations (e.g., via APIs) that allow for processing access requests in combination. In operation, by way of example, the dSAS includes a dSAS portal (e.g., graphical user interface or REST API command interface) where a storage account can be selected. The storage account can be associated with attributes that support configuring the temporary access to the storage account. For example, upon selecting the storage account at the dSAS portal, the user can further select a Subscription ID and an access level. Additional granularity in certain access level is contemplated (e.g., Blobs, Queues, or tables). The dSAS portal can further request a user to validate the input prior to submitting their request.

dSAS and dSMS in collaboration can operate to validate a temporary access request to validate the request for access to a resource. For example, “validate_Storage_Account” function and a Subscription ID and Storage Account tuple are implemented to validate the access request. The validation of the access request can further include the dSMS returning the location of an application SAS key if the validation operation is successful. dSAS, upon submission of a validated temporary access request, the policy (e.g., policy file) for the particular request (e.g., Subscription ID, Storage Account) is accessed to provide the appropriate user access. Upon approval of the temporary access request, the dSAS sends a SAS key request to the dSMS 110 to retrieve the SAS key, which is transmitted to the user. The SAS key request from the dSAS includes an expiration period for the SAS key. For example, the policy file for the request is parsed for a length of time specific to the <Subscription ID, Storage Account> tuple. It is also contemplated that there may be a default expiration time periods for temporary access requests. The dSAS may be required to authenticate with the dSTS for making requests to the dSMS as a security precaution operation.

Accordingly, dSAS may operate primarily to provide access requests and communicate with dSMS for SAS keys. dSMS in turn provides autonomous secret management as described herein. For example, any SASes which depend upon a storage account key can be generated and/or rolled over based on the expirations of the storage account keys. For example, dSMS can define an active key as the key which has farther expiration (i.e. the key which is valid for the longer period of time). As such, dSMS can generate any SASes using the active key. Moreover, any SASes which depend upon a storage account key can be rolled over prior to rolling over the key upon which they depend. For example, if a first storage account key is being rolled over, dSMS can regenerate any dependent SASes using the other key prior to rolling over the first key. In some embodiments, timer workers can be used to autonomously renew storage account keys and/or autonomously regenerate SASes.

Accordingly, a method for managing temporary shared access signature services includes receiving, at a secrets management service (“SMS”), from a temporary SAS service, a validation request to validate a temporary access request for an account resource. The validation request comprises an account identifier, where validating the temporary access request operates as an indication that the account is supported via the SMS for providing temporary access to account resources. The method further includes determining that an account associated with the validation request is further associated with a corresponding storage location of a SAS key for authenticating temporary access to account resources for the account. Determining that the account corresponds to the storage location of the SAS key for authenticating temporary access to account resources operates as an indication that the SMS manages automatic renewal of one or more keys based on a rollover policy.

The method includes communicating the storage location for the SAS key as validation of the temporary access request. The method also includes receiving, from the temporary SAS service, a SAS key request for the SAS key. The SAS key request further comprises at least a portion of an access policy, wherein the portion of the access policy indicates an expiration time associated the SAS key being requested. The method includes communicating the SAS key to the temporary SAS service. The SAS key is associated with a storage account key, and wherein the SMS automatically renewing the storage account key comprises generating a secrets package comprising regenerated shared access keys.

In another embodiment, a method for managing temporary shared access signatures services receiving, from a client device, input for a temporary access request for an account resource of an account. The input, comprising a subscription identifier and a storage account identifier, for a temporary access request for the account resource of the account, is received via a client device accessing a graphical user interface to the temporary SAS service.

In some embodiments, the method includes communicating a validation request to validate the temporary access request and receiving a storage location for the SAS key as validation of the temporary access request. The validation request comprises an account identifier, where validating the temporary access request operates as an indication that the account is supported via the SMS for providing temporary access to account resources.

The method includes accessing an access policy associated with the temporary access request. The method also includes communicating a shared access signature “SAS” key request to a secrets management service (“SMS”), the SAS request comprising at least a portion of the access policy, and wherein the SMS automatically renews one or more keys associated with granting temporary access requests. The method further includes receiving an SAS key from the SMS and communicating the SAS key to the client device. The SAS key is associated with a storage account key and the SMS automatically renewing the storage account key comprises generating a secrets package comprising regenerated shared access keys. The portion of the access policy indicates an expiration time associated the SAS key being requested.

Example Flow Diagrams

With reference to FIGS. 6-15, flow diagrams are provided illustrating methods for managing secrets in a distributed computing environment. The methods can be performed using the autonomous secrets management system described herein. In embodiments, one or more computer storage media having computer-executable instructions embodied thereon can, when executed by one or more processors, cause the one or more processors to perform the methods in the autonomous secrets management system.

Turning now to FIG. 6, a flow diagram is provided that illustrates a method 600 for managing secrets in a distributed computing environment using a secrets management service. Initially at block 610, a specified secret for a deployed service and a rollover policy for the secret are received at a secrets management service (“SMS”). At block 620, the secret is installed in a first secrets store of the SMS. At block 630, the secret is provided by the SMS to facilitate an initial deployment of the service to an agent on a node in a distributed computing environment. The initial deployment comprises installing the secret in a second secrets store of the node. At block 640, the secret is automatically renewed in the first secret store by the SMS, pursuant to the specified rollover policy. At block 650, in response to receiving a periodic polling request from a credentials management component associated with the agent, the renewed secret is released to the credentials management component.

Turning now to FIG. 7, a flow diagram is provided that illustrates a method 700 for agent state tracking. Initially at block 710, in response to delivering the renewed secret to the agent, a first state of an agent is set indicating delivery of the renewed secret to the agent. At block 720, in response to receiving, in a subsequent periodic polling request, metadata indicating the renewed secret is installed in the second secret store of the node, a second state of the agent is set indicating the delivery is confirmed.

Turning now to FIG. 8, a flow diagram is provided that illustrates a method 800 for rollover tracking. Initially at block 810 a first rollover state is set indicating the rollover has begun. At block 820, in response to determining that a corresponding internal state for each of a plurality of agents associated with the service has been set to the second state, a second rollover state is set indicating the rollover is complete.

Turning now to FIG. 9, a flow diagram is provided that illustrates a method 900 for managing secrets using a secrets management service. Initially at block 910, a secret is received at an agent of a node as part of an initial deployment of a service associated with the node. At block 920, the secret is installed in a secrets store of the node. At block 930, a secrets management service (“SMS”) is periodically polled for an automatically renewed version of the secret by providing the SMS with metadata indicating a current version of the secret on the node. At block 940, in response to receiving the renewed version of the secret, the renewed secret is installed in the secrets store without redeploying the service.

Turning now to FIG. 10, a flow diagram is provided that illustrates a method 1000 for automatic rollover of client certificates. Initially at block 1010, a client certificate is deployed to a client app. The client app is configured to authenticate with a service app by presenting the client certificate to the service app. At block 1020, the client certificate is automatically renewed by requesting a renewed certificate from a certificate authority. At block 1030, in response to receiving a first periodic polling request from the service app at a public end point of the SMS, a public key of the renewed certificate is released to the service app. At block 1040, in response to receiving a second periodic polling request from the client app at a trusted end point of the SMS, a private key of the renewed certificate is released to the client app.

Turning now to FIG. 11, a flow diagram is provided that illustrates a method 1100 for managing secrets across scope boundaries. Initially at block 1110, a specified secret for a deployed service and a rollover policy for the secret are received at a cross-scope secrets management service (“cross-scope SMS”). At block 1120, the secret is installed in a first secrets store of the cross-scope SMS. At block 1130, in response to the cross-scope SMS receiving an initial polling request from a local secrets management service (“local SMS”), the secret is released to the local SMS to facilitate an initial deployment of the service to a local scope of the local SMS in a distributed computing environment. At block 1140, the secret in the first secret store is automatically renewed by the cross-scope SMS, pursuant to the specified rollover policy. At block 1150, in response to the cross-scope SMS receiving a periodic polling request from the local SMS, the renewed secret is released to the local SMS to facilitate distribution of the renewed secret to the local scope by the local SMS.

Turning now to FIG. 12, a flow diagram is provided that illustrates a method 1200 for managing secrets across regional boundaries. Initially at block 1210, an input specifying a path of a secret in a first secret store of a cross-regional secrets management service (“cross-regional SMS”) is received by a regional secrets management service (“regional SMS”). At block 1220, the secret is received by the regional SMS from the cross-regional SMS. At block 1230, the secret is distributed by the regional SMS to facilitate an initial deployment of an associated service to a regional scope of the regional SMS in a distributed computing environment. At block 1240, the cross-regional SMS is periodically polled by the regional SMS for an automatically renewed version of the secret stored in the first secret store. At block 1250, the renewed secret is received by the regional SMS from the cross-regional SMS. At block 1260, in response to the regional SMS receiving a periodic polling request from a container within the regional scope associated with the service, the renewed secret is released to the container.

Turning now to FIG. 13, a flow diagram is provided that illustrates a method 1300 for managing secrets across scope boundaries. Initially at block 1310, an input is received by a cross-scope secrets management service (“cross-scope SMS”). The input specifies secrets including a primary storage account key and a secondary storage account key for a deployed service. The input also includes a rollover policy specifying interleaving expirations of the primary and secondary keys. At block 1320, the secrets are installed in a first secrets store of the cross-scope SMS. At block 1330, one of the storage account keys with a farther expiration is designated as an active key. At block 1340, the secrets are automatically renewed by the cross-scope SMS by automatically renewing a remaining one of the storage account keys in the first secret store pursuant to the specified rollover policy.

At block 1350, an input specifying a path of the secrets in the first secret store of the cross-scope SMS is received by a local secrets management service (“local SMS”). At block 1360, the secrets are fetched by the local SMS from the cross-scope SMS. At block 1370, the secrets are distributed to facilitate an initial deployment of the service to a local scope of the local SMS in a distributed computing environment. At block 1380, the renewed secrets are fetched by the local SMS periodically polling the cross-scope SMS. At block 1390, in response to the local SMS receiving a periodic polling request from a container within the local scope associated with the service, the renewed secrets are released by the local SMS to the container.

Turning now to FIG. 14A, a flow diagram is provided that illustrates a method 1400A for managing secrets across scope boundaries. Initially at block 1410A, a first token request for a token is received from a managed service. The token supports authenticating a managed service for performing operations in a distributed computing environment. The first token request comprises an identity identifier of the managed service. At block 1420A, based on the identity identifier, a secret for the managed service is identified. A secret management service (“SMS”) operates to automatically renew secrets including the secret. At block 1430A, a secret token service associated with the identity identifier is determined. At block 1440A, a second token request comprising the secret is communicated to the secret token service. At block 1450A, the token is received from the secret token service. At block 1460A, the token is communicated to the managed service.

Turning now to FIG. 14B, a flow diagram is provided that illustrates a method 1400B for managing secrets across scope boundaries. Initially at block 1410B, a first token request for a token is generated at a managed service. The token supports authenticating the managed service in a distributed computing environment. The first token request comprises an identity identifier of the managed service. The token is retrievable based on a secret that is associated with a secrets management service (“SMS”) for autonomous management of the secret. At block 1420B, the first token request to a credentials manager is communicated. At block 1430B, based on communicating the first token request to the credentials manager, a token is received from a secret token service. The token is received based in part on the credentials manager generating a second token request for the token and communicating the second token request and a secret associated with the managed service to the secret token service.

Turning now to FIG. 15A, a flow diagram is provided that illustrates a method 1500A for managing secrets across scope boundaries. Initially at block 1510A, block 1510A, input for a temporary access request for an account resource of an account is received from a client device. In some embodiments, an access policy associated with the temporary access request is accessed to determine an expiration period and additional access policy requirements for granting temporary access to the account resource. At block 1520A, a shared access signature “SAS” key request is communicated to a secrets management service (“SMS”). The SAS key request comprises at least a portion of the access policy. The SMS automatically renews one or more keys associated with granting temporary access requests. At block 1530B, the SAS key is received from the SMS. At block 1540B, the SAS key is communicated to the client to the client device.

Turning now to FIG. 15B, a flow diagram is provided that illustrates a method 1500B for managing secrets across scope boundaries. Initially at block 1510B, a validation request to validate a temporary access request for an account resource is received, at a secrets management service (“SMS”), from a temporary SAS service. At block 1520B, it is determined that an account associated with the validation request is further associated with a corresponding storage location of a SAS key for authenticating temporary access to account resources for the account. At block 1530B, the storage location for the SAS key is communicated as validation of the temporary access request. At block 1540B, a SAS key request for the SAS key is received from the temporary SAS service. At block 1550B, the SAS key is communicated to the temporary SAS service.

Example Distributed Computing Environment

Referring now to FIG. 16, FIG. 16 illustrates an example distributed computing environment 1600 in which implementations of the present disclosure may be employed. In particular, FIG. 16 shows a high level architecture of the secrets management system (“system”) in cloud computing platform 1610, where the system supports seamless modification of software component. It should be understood that this and other arrangements described herein are set forth only as examples. For example, as described above, many of the elements described herein may be implemented as discrete or distributed components or in conjunction with other components, and in any suitable combination and location. Other arrangements and elements (e.g., machines, interfaces, functions, orders, and groupings of functions, etc.) can be used in addition to or instead of those shown.

Data centers can support distributed computing environment 1600 that includes cloud computing platform 1610, rack 1620, and node 1630 (e.g., computing devices, processing units, or blades) in rack 1620. The system can be implemented with cloud computing platform 1610 that runs cloud services across different data centers and geographic regions. Cloud computing platform 1610 can implement fabric controller 1640 component for provisioning and managing resource allocation, deployment, upgrade, and management of cloud services. Typically, cloud computing platform 1610 acts to store data or run service applications in a distributed manner. Cloud computing infrastructure 1610 in a data center can be configured to host and support operation of endpoints of a particular service application. Cloud computing infrastructure 1610 may be a public cloud, a private cloud, or a dedicated cloud.

Node 1630 can be provisioned with host 1650 (e.g., operating system or runtime environment) running a defined software stack on node 1630. Node 1630 can also be configured to perform specialized functionality (e.g., compute nodes or storage nodes) within cloud computing platform 1610. Node 1630 is allocated to run one or more portions of a service application of a tenant. A tenant can refer to a customer utilizing resources of cloud computing platform 1610. Service application components of cloud computing platform 1610 that support a particular tenant can be referred to as a tenant infrastructure or tenancy. The terms service application, application, or service are used interchangeably herein and broadly refer to any software, or portions of software, that run on top of, or access storage and compute device locations within, a datacenter.

When more than one separate service application is being supported by nodes 1630, nodes 1630 may be partitioned into virtual machines (e.g., virtual machine 1652 and virtual machine 1654). Physical machines can also concurrently run separate service applications. The virtual machines or physical machines can be configured as individualized computing environments that are supported by resources 1660 (e.g., hardware resources and software resources) in cloud computing platform 1610. It is contemplated that resources can be configured for specific service applications. Further, each service application may be divided into functional portions such that each functional portion is able to run on a separate virtual machine. In cloud computing platform 1610, multiple servers may be used to run service applications and perform data storage operations in a cluster. In particular, the servers may perform data operations independently but exposed as a single device referred to as a cluster. Each server in the cluster can be implemented as a node.

Client device 1680 may be linked to a service application in cloud computing platform 1610. Client device 1680 may be any type of computing device, which may correspond to computing device 1600 described with reference to FIG. 16, for example. Client device 1680 can be configured to issue commands to cloud computing platform 1610. In embodiments, client device 1680 may communicate with service applications through a virtual Internet Protocol (IP) and load balancer or other means that direct communication requests to designated endpoints in cloud computing platform 1610. The components of cloud computing platform 1610 may communicate with each other over a network (not shown), which may include, without limitation, one or more local area networks (LANs) and/or wide area networks (WANs).

Example Computing Environment

Having briefly described an overview of embodiments of the present invention, an exemplary operating environment in which embodiments of the present invention may be implemented is described below in order to provide a general context for various aspects of the present invention. Referring initially to FIG. 17 in particular, an exemplary operating environment for implementing embodiments of the present invention is shown and designated generally as computing device 1700. Computing device 1700 is but one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should computing device 1700 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated.

The invention may be described in the general context of computer code or machine-useable instructions, including computer-executable instructions such as program modules, being executed by a computer or other machine, such as a personal data assistant or other handheld device. Generally, program modules including routines, programs, objects, components, data structures, etc. refer to code that perform particular tasks or implement particular abstract data types. The invention may be practiced in a variety of system configurations, including hand-held devices, consumer electronics, general-purpose computers, more specialty computing devices, etc. The invention may also be practiced in distributed computing environments where tasks are performed by remote-processing devices that are linked through a communications network.

With reference to FIG. 17, computing device 1700 includes bus 1710 that directly or indirectly couples the following devices: memory 1712, one or more processors 1714, one or more presentation components 1716, input/output ports 1718, input/output components 1720, and illustrative power supply 1722. Bus 1710 represents what may be one or more buses (such as an address bus, data bus, or combination thereof). The various blocks of FIG. 17 are shown with lines for the sake of conceptual clarity, and other arrangements of the described components and/or component functionality are also contemplated. For example, one may consider a presentation component such as a display device to be an I/0 component. Also, processors have memory. We recognize that such is the nature of the art, and reiterate that the diagram of FIG. 17 is merely illustrative of an exemplary computing device that can be used in connection with one or more embodiments of the present invention. Distinction is not made between such categories as “workstation,” “server,” “laptop,” “hand-held device,” etc., as all are contemplated within the scope of FIG. 17 and reference to “computing device.”

Computing device 1700 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by computing device 1700 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media.

Computer storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 1700. Computer storage media excludes signals per se.

Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.

Memory 1712 includes computer storage media in the form of volatile and/or nonvolatile memory. The memory may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard drives, optical-disc drives, etc. Computing device 1700 includes one or more processors that read data from various entities such as memory 1712 or I/O components 1720. Presentation component(s) 1716 present data indications to a user or other device. Exemplary presentation components include a display device, speaker, printing component, vibrating component, etc.

I/O ports 1718 allow computing device 1700 to be logically coupled to other devices including 1/0 components 1720, some of which may be built in. Illustrative components include a microphone, joystick, game pad, satellite dish, scanner, printer, wireless device, etc.

With reference to the autonomous secrets management system, embodiments described herein support autonomous renewal and distribution of secrets. The autonomous secrets management system components refer to integrated components for autonomous renewal and distribution of secrets. The integrated components refer to the hardware architecture and software framework that support functionality within the system. The hardware architecture refers to physical components and interrelationships thereof and the software framework refers to software providing functionality that can be implemented with hardware embodied on a device.

The end-to-end software-based system can operate within the system components to operate computer hardware to provide system functionality. At a low level, hardware processors execute instructions selected from a machine language (also referred to as machine code or native) instruction set for a given processor. The processor recognizes the native instructions and performs corresponding low level functions relating, for example, to logic, control and memory operations. Low level software written in machine code can provide more complex functionality to higher levels of software. As used herein, computer-executable instructions includes any software, including low level software written in machine code, higher level software such as application software and any combination thereof. In this regard, the system components can manage resources and provide services for system functionality. Any other variations and combinations thereof are contemplated with embodiments of the present invention.

By way of example, the autonomous secrets management system can include an API library that includes specifications for routines, data structures, object classes, and variables may support the interaction between the hardware architecture of the device and the software framework of the autonomous secrets management system. These APIs include configuration specifications for the autonomous secrets management system such that the different components therein can communicate with each other in the autonomous secrets management system, as described herein.

Having identified various components utilized herein, it should be understood that any number of components and arrangements may be employed to achieve the desired functionality within the scope of the present disclosure. For example, the components in the embodiments depicted in the figures are shown with lines for the sake of conceptual clarity. Other arrangements of these and other components may also be implemented. For example, although some components are depicted as single components, many of the elements described herein may be implemented as discrete or distributed components or in conjunction with other components, and in any suitable combination and location. Some elements may be omitted altogether. Moreover, various functions described herein as being performed by one or more entities may be carried out by hardware, firmware, and/or software, as described below. For instance, various functions may be carried out by a processor executing instructions stored in memory. As such, other arrangements and elements (e.g., machines, interfaces, functions, orders, and groupings of functions, etc.) can be used in addition to or instead of those shown.

Embodiments described in the paragraphs below may be combined with one or more of the specifically described alternatives. In particular, an embodiment that is claimed may contain a reference, in the alternative, to more than one other embodiment. The embodiment that is claimed may specify a further limitation of the subject matter claimed.

The subject matter of embodiments of the invention is described with specificity herein to meet statutory requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways, to include different steps or combinations of steps similar to the ones described in this document, in conjunction with other present or future technologies. Moreover, although the terms “step” and/or “block” may be used herein to connote different elements of methods employed, the terms should not be interpreted as implying any particular order among or between various steps herein disclosed unless and except when the order of individual steps is explicitly described.

For purposes of this disclosure, the word “including” has the same broad meaning as the word “comprising,” and the word “accessing” comprises “receiving,” “referencing,” or “retrieving.” Further the word “communicating” has the same broad meaning as the word “receiving,” or “transmitting” facilitated by software or hardware-based buses, receivers, or transmitters using communication media described herein. In addition, words such as “a” and “an,” unless otherwise indicated to the contrary, include the plural as well as the singular. Thus, for example, the constraint of “a feature” is satisfied where one or more features are present. Also, the term “or” includes the conjunctive, the disjunctive, and both (a or b thus includes either a or b, as well as a and b).

For purposes of a detailed discussion above, embodiments of the present invention are described with reference to a distributed computing environment; however the distributed computing environment depicted herein is merely exemplary. Components can be configured for performing novel aspects of embodiments, where the term “configured for” can refer to “programmed to” perform particular tasks or implement particular abstract data types using code. Further, while embodiments of the present invention may generally refer to the autonomous secrets management system and the schematics described herein, it is understood that the techniques described may be extended to other implementation contexts.

Embodiments of the present invention have been described in relation to particular embodiments which are intended in all respects to be illustrative rather than restrictive. Alternative embodiments will become apparent to those of ordinary skill in the art to which the present invention pertains without departing from its scope.

From the foregoing, it will be seen that this invention is one well adapted to attain all the ends and objects hereinabove set forth together with other advantages which are obvious and which are inherent to the structure.

It will be understood that certain features and sub-combinations are of utility and may be employed without reference to other features or sub-combinations. This is contemplated by and is within the scope of the claims. 

What is claimed is:
 1. A method for managing temporary shared access signature (“SAS”) services, the method comprising: receiving, at a secrets management service (“SMS”), from a temporary SAS service, a validation request to validate a temporary access request for an account resource; determining that an account associated with the validation request is further associated with a corresponding storage location of a SAS key for authenticating temporary access to account resources for the account; communicating the storage location for the SAS key as validation of the temporary access request; receiving, from the temporary SAS service, a SAS key request for the SAS key; and communicating the SAS key to the temporary SAS service.
 2. The method of claim 1, wherein the validation request comprises an account identifier, wherein validating the temporary access request operates as an indication that the account is supported via the SMS for providing temporary access to account resources.
 3. The method of claim 1, wherein determining that the account corresponds to the storage location of the SAS key for authenticating temporary access to account resources operates as an indication that the SMS manages automatic renewal of one or more keys based on a rollover policy.
 4. The method of claim 1, wherein the SAS key request further comprises at least a portion of an access policy, wherein the portion of the access policy indicates an expiration time associated the SAS key being requested.
 5. The method of claim 1, wherein the SAS key is associated with a primary storage account key and a secondary storage account key, and wherein a rollover policy specifies interleaving expirations of the primary and secondary keys.
 6. The method of claim 1, wherein the SAS key is associated with a storage account key, and wherein the SMS automatically renewing the storage account key comprises generating a secrets package comprising regenerated shared access keys.
 7. The method of claim 1, wherein input, for a temporary access request for an account resource of an account, is received via a client device having a graphical user interface to the temporary SAS service.
 8. One or more computer storage media storing computer-useable instructions that, when used by one or more computing devices, cause the one or more computing devices to perform operations comprising: receiving, from a client device, input for a temporary access request for an account resource of an account; accessing an access policy associated with the temporary access request; communicating a shared access signature “SAS” key request to a secrets management service (“SMS”), the SAS request comprising at least a portion of the access policy, and wherein the SMS automatically renews one or more keys associated with granting temporary access requests; receiving an SAS key from the SMS; and communicating the SAS key to the client device.
 9. The media of claim 8, further comprising: communicating a validation request to validate the temporary access request; and receiving a storage location for the SAS key as validation of the temporary access request.
 10. The media of claim 9, the operation further comprising receiving, from the temporary SAS service, the validation request to validate the temporary access request; determining that the account associated with the validation request is further associated with the storage location of the SAS key for temporary access to account resources for the account; communicating the storage location for the SAS key as validation of the temporary access request; receiving, from the temporary SAS service, the SAS key request for the SAS key; and communicating the SAS key to the temporary SAS service.
 11. The media of claim 9, wherein the validation request comprises an account identifier, wherein validating the temporary access request operates as an indication that the account is supported via the SMS for providing temporary access to account resources.
 12. The media of claim 8, wherein determining that the account corresponds to a storage location of the SAS key for authenticating temporary access to account resources operates as an indication that the SMS manages automatic renewal of one or more keys based on a rollover policy.
 13. The media of claim 8, wherein the input comprising a subscription identifier and a storage account identifier, for a temporary access request for the account resource of the account, is received via a client device accessing a graphical user interface to the temporary SAS service.
 14. The media of claim 8, wherein the SAS key is associated with a storage account key, and wherein the SMS automatically renewing the storage account key comprises generating a secrets package comprising regenerated shared access keys.
 15. The media of claim 8, wherein the portion of the access policy indicates an expiration time associated the SAS key being requested.
 16. A computer system comprising: one or more hardware processors and memory configured to provide computer program instructions to the one or more hardware processors; a temporary shared access signature service (“SAS”) configured to utilize the one or more hardware processors to: receive, from a client device, input for a temporary access request for an account resource of an account; communicate a validation request to validate the temporary access request; receive a storage location for the SAS key as validation of the temporary access request; access an access policy associated with the temporary access request; communicate a SAS key request to a secrets management service (“SMS”), the SAS request comprising at least a portion of the access policy, and wherein the SMS automatically renews one or more keys associated with granting temporary access requests; receive an SAS key from the SMS; and communicate the SAS key to the client.
 17. The computer system of claim 16, further comprising a secrets management service (“SMS”) to configured to utilize the one or more hardware processors to: receive, from the temporary SAS service, the validation request to validate the temporary access request; determine that the account associated with the validation request is further associated with the storage location of the SAS key for temporary access to account resources for the account; communicate the storage location for the SAS key as validation of the temporary access request; receive, from the temporary SAS service, the SAS key request for the SAS key; and communicating the SAS key to the temporary SAS service.
 18. The computer system of claim 16, wherein determining that the account corresponds to a storage location of the SAS key for authenticating temporary access to account resources operates as an indication that the SMS manages automatic renewal of one or more keys based on a rollover policy.
 19. The computer system of claim 16, wherein the SAS key request further comprises at least a portion of an access policy, wherein the portion of the access policy indicates an expiration time associated the SAS key being requested.
 20. The computer system of claim 16, wherein the SAS key is associated with a storage account key, and wherein the SMS automatically renewing the storage account key comprises generating a secrets package comprising regenerated shared access keys. 